Intellectual asset automatic docketing and file association

ABSTRACT

One embodiment of the invention includes a method of associating a file with an intellectual asset record. The method includes reading information such as the file name and metadata pertaining to a file. The file name has a predetermined format made up of fields. The fields in the file name and the metadata are extracted. Based upon the fields, the file is linked to intellectual asset record. The intellectual asset record includes a set of related data organized into meaningful units pertaining to an intellectual asset.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of and priority to U.S. ProvisionalApplication No. 61/428,526 filed on Dec. 30, 2010, entitled“Intellectual Asset Automatic Docketing and File Association”; U.S.Provisional Application No. 61/476,567, filed on Apr. 18, 2011, entitled“Method and server for Improved Intellectual Asset Docketing”; and U.S.Provisional Application No. 61/452,382, filed on Mar. 14, 2011, entitled“Method and Server for Related Art Citation Management”. The disclosuresof all three provisional applications are incorporated herein byreference.

BACKGROUND

1. The Field of the Invention

Embodiments relate generally to intellectual asset docketing andmanagement and more particularly to a method and system for intellectualasset automatic docketing and file association.

2. The Relevant Technology

A docketing system is used to schedule legal matters and manage aspectsof intellectual property assets. Examples of intellectual propertyassets may include: patents, trade secrets, publications, trademarks,domain names, copyrights, and applications or filings thereof. Anintellectual asset management system typically supports docketing andother related activities in the full lifecycle of intellectual propertyassets, such as invention disclosure submission, trademark searchrequests, multi-party collaboration, document and e-mail management,configurable business workflow rules, and business intelligence tools,among other features. An intellectual asset management system providesvisibility and access to internal and external participants in theintellectual asset management process—for example, attorneys, agents andparalegals, researchers and engineers, portfolio managers, marketing,licensing professionals and other business managers.

A challenge facing docketing users of intellectual asset managementsystems is the association of documentation with intellectual propertyassets within the docketing systems. It is possible for one intellectualproperty asset to have hundreds, if not thousands, of associateddocumentation files. For example, drafting, filing, and prosecuting apatent application can generate numerous associated documents, such asthe original invention disclosure, patent application drafts, drawings,ancillary patent filing documents, and patent prosecution office actionsand responses. To store and associate all these various documents withan intellectual property asset within a docketing or intellectual assetmanagement system can be a time-consuming and error-prone process.

Additional challenges for users of docketing and intellectual assetmanagement systems are assigning appropriate tasks and recordingprosecution items for docketing. For example, during patent applicationprosecution, it is generally important for a patent applicant or itslegal representation to keep up-to-date on the status of the prosecutionwith a patent office, and to provide appropriate documentation andoffice action responses in a timely manner. A docketing solution canprovide, among other things, recordation of this prosecution and theassociated tasks assigned to the applicant or assigned agent(s) managingthe prosecution so as to properly schedule actions that need to betaken, thereby helping to avoid paying late fees and losing rights toprotect use of the associated invention.

The subject matter claimed herein is not limited to embodiments thatsolve any disadvantages or that operate only in environments such asthose described above. Rather, this background is only provided toillustrate one exemplary technology area where some embodimentsdescribed herein may be practiced.

BRIEF SUMMARY OF SOME EXAMPLE EMBODIMENTS

Embodiments relate generally to intellectual asset docketing andmanagement and more particularly to a method and system for intellectualasset automatic docketing and file association.

One embodiment of the invention includes a method of associating a filewith an intellectual asset record. The method includes readinginformation such as the file name and metadata pertaining to a file. Thefile name has a predetermined format made up of fields. The fields inthe file name and the metadata are extracted. Based upon the fields, thefile is linked to an intellectual asset record. The intellectual assetrecord includes a set of related data organized into meaningful unitspertaining to an intellectual asset.

Another embodiment includes a method of associating a file with anintellectual asset record. The intellectual asset record includes a setof related data organized into meaningful units pertaining to anintellectual asset. The steps of the method include reading informationpertaining to a file such as metadata and a file name having apredetermined format. The format of the filename includes a referenceidentifier, a document date, and a document code reference.Additionally, the filename and the metadata are extracted. Based upon acorrespondency between a record identifier and the reference identifier,the file is linked to the intellectual asset record. The recordidentifier is one meaningful unit of the set of related data organizedinto meaningful units and is an identifier uniquely identifying theintellectual asset record. Additionally, the document date is stored inthe intellectual asset record as a document date value.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential characteristics of the claimed subject matter, nor is itintended to be used as an aid in determining the scope of the claimedsubject matter.

Additional features and advantages of the invention will be set forth inthe description which follows, and in part will be obvious from thedescription, or may be learned by the practice of the invention. Thefeatures and advantages of the invention may be realized and obtained bymeans of the instruments and combinations particularly pointed out inthe appended claims. These and other features of the present inventionwill become more fully apparent from the following description andappended claims, or may be learned by the practice of the invention asset forth hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

To further clarify the above and other advantages and features of thepresent invention, a more particular description of the invention willbe rendered by reference to specific embodiments thereof which areillustrated in the appended drawings. It is appreciated that thesedrawings depict only typical embodiments of the invention and aretherefore not to be considered limiting of its scope. The invention willbe described and explained with additional specificity and detailthrough the use of the accompanying drawings in which:

FIG. 1 illustrates an example docketing system including a docketingserver;

FIG. 2A illustrates an example docketing server of the docketing systemof FIG. 1;

FIG. 2B illustrates example data that may be stored as part of anintellectual asset record on the docketing server of FIG. 2A;

FIG. 3 illustrates an example system for automatically associating afile with an intellectual asset record and for automatically adding oneor more tasks or prosecution items to an intellectual asset record;

FIG. 4A illustrates an example user interface object providing detailson tasks associated with an intellectual asset record;

FIG. 4B illustrates an example task template;

FIG. 4C illustrates an example user interface object used to add aprosecution item to an intellectual asset record;

FIG. 4D illustrates an example prosecution template;

FIG. 4E illustrates an example user interface object providing detailson documents associated with an intellectual asset record and providinga method for a docketing user to upload a document to an intellectualasset record;

FIG. 5 illustrates an example document code item;

FIG. 6 illustrates an example predetermined format of a file name;

FIG. 7 illustrates an example method for automatically associating afile with an intellectual asset record and for automatically adding oneor more tasks or prosecution items to an intellectual asset record; and

FIG. 8 provides a brief, general description of a suitable computingenvironment in which several embodiments may be implemented.

DETAILED DESCRIPTION OF SOME EXAMPLE EMBODIMENTS

Example embodiments of the invention relate to intellectual assetdocketing and management. More particularly, example embodiments relateto a method and docketing system for intellectual asset automaticdocketing and file association. The example systems disclosed herein canenable the file association and automatic docketing with an intellectualasset record based on information pertaining to the file such as a filename or metadata. In an example embodiment, a file name of a file mayhave a predetermined format including fields. The fields may be areference identifier, which allows the system to associate the file withthe intellectual asset record; a document date, which is stored as thedocument date value of the intellectual asset record; and a documentcode reference, which can be matched to templates used to create tasksand prosecution items in the intellectual asset record.

FIG. 1 illustrates an example docketing system 100. The docketing system100 may include a user device 110, a computer network 120, and adocketing server 130. The user device 110 is operably connected to allowa docketing user (not shown) access to a docketing service (not shown)through communication via the computer network 120 with the docketingserver 130.

The docketing service generally schedules legal matters and managesaspects of those legal matters. For example, an intellectual propertydocking service may support scheduling a disclosure submission andmanage the related filing dates such as provisional application filing,non-provisional conversion dates, maintenance fees, and the like. Themanagement and scheduling of these legal matters may be managed by adocketing server application (described below) which may include a setof templates, data, instructions, applications, or computer programs.Alternatively or additionally, the docketing system 100 may provide avisible, accessible, user-interface to internal and external entitiesthrough which the legal matters are manually managed.

The user device 110 in FIG. 1 may be a desktop computer, a laptopcomputer, a portable electronic device such as a cellular/mobile/smartphone, a tablet personal computer, a personal digital assistant or anyequivalent device. The user device 110 may include a docketing clientsoftware to access the docketing server 130, or the user device 110 mayinclude a web browser to access the docketing server 130, where thedocketing server 130 provides the docketing service as a webapplication. Alternatively, the user device 110 may communicate with thedocketing server 130 through other means, such as a remote desktopconnection.

Additionally, the user device 110 communicates with the docketing server130 via the computer network 120. The computer network 120 relates to acollection of devices interconnected by communication channels thatallows sharing of information among the interconnected devices. In thisexample embodiment, the computer network 120 may be or include any wiredor wireless network technology such as optical fiber, electrical cables,Ethernet, radio wave, microwaves, infrared transmission, wirelessinternet, communication satellites, cellular telephone signals, or anequivalent networking signal that interfaces with devices to createnetwork. Specifically, in one embodiment, the user device 110communicates with the docketing server 130 via the internet. In otherembodiments, the user device 110 may be directly coupled with thedocketing server 130 and/or may be integrated directly with, and be apart of, the docketing server 130.

In FIG. 1, one user device 110 is operably connected to communicate withthe docketing server 130 via the computer network 120. However, inalternative embodiments a plurality of user devices 110 which mayinclude various types of user devices 110 may simultaneously communicatewith the docketing server 130. Additionally or alternatively, thedocketing system 100 may include multiple docketing servers 130 whichare operably connected to communicate information among the multipledocketing servers 130 and/or to communicate information among varioususer devices 110 operably connected to communicate with the docketingservers 130.

Turning next to FIG. 2A, additional details of the docketing server 130are illustrated. As depicted in FIG. 2A, the docketing server 130 mayinclude a controller 132, and a memory device 134. The controller 132may include a microprocessor 140 which executes a docketing serverapplication (not shown). The docketing server application may includetemplates, data, instructions, applications, or computer programs storedin a memory device 134. The docketing server application may vary asnecessary to implement the docketing service.

In the embodiment illustrated in FIG. 2A, the controller 132 isoperatively coupled to the memory device 134, which enables thecontroller 132 through the microprocessor 140 to access informationstored on the memory device 134 such as the docketing serverapplications, an intellectual asset record (described below), and/or afile (described below). The memory device 134 may provide data to thecontroller 132 in various forms, such as, but not limited to, databaserecords, files, bitstreams, and bytestreams, and the memory device 134may comprise volatile or non-volatile memory or storage.

As illustrated in FIG. 2A, the docket server 130 can include a singlecontroller 132, which can include a microprocessor 140 that executes adocketing server application, and a single memory device 134. However,in alternative embodiments, the docket server 130 may include one ormore controllers 132, one or more microprocessors 140 which execute aplurality of docketing server applications, and one or more memorydevices 134. The one or more memory devices 134 may be remotely locatedfrom each other and/or from the controller 132.

The docketing server 130 can include a communication interface 136. Thecommunication interface 136 enables the docketing server 130 tocommunicate with the user device 110 (FIG. 1) via the computer network120 (FIG. 1). Additionally, the communication interface 136 may enablethe docketing server 130 to communicate with other docketing serverapplications either publically or privately available on the internet orthrough an interface between multiple docketing servers 130 which areoperably connected via the computer network 120. Examples of thecommunication interface 136 include any receiver or transmitter capableof functioning with the computer network 120.

The docketing server 130 may further include a display 138 and one ormore input devices 139. The docketing user (not shown) and/or adocketing server administrator (not shown) may directly interface andcontrol the docketing server 130 through the display 138 and the inputdevices 139. Examples of the display 138 may include a thin filmtransistor liquid crystal display, liquid crystal display or anequivalent structure. Examples of the input devices 139 may include aQWERTY key pad, a ten key input pad, a mouse, a stylus, voicerecognition software, an audio mixer, or may be integrated with thedisplay 138 as in a touchscreen device using a surface acoustic wave,surface capacitance, projected capacitance, or an equivalent structure.

Turning next to FIG. 2B, additional details of the memory device 134 aredisclosed. FIG. 2B illustrates data that may be stored in the memorydevice 134. Specifically, in an embodiment of the docketing server 130used in an intellectual asset management system, which can supportdocketing and other related activities of intellectual property assets,the data may include intellectual asset records 200 and/or files 205.

In alternative embodiments, the files 205 and the intellectual assetrecords 200 may be stored separately. For example, the files 205 may bestored on a first memory device and the intellectual asset records 200may be stored on a second memory device. In this example, the firstmemory device may be located in the docketing server 130 (FIG. 2A) andthe second memory device may be located in a remote site. Alternatively,the file 205 and the intellectual asset record 200 may both be stored ona same memory device 134. Other data may additionally or alternativelybe stored in the memory device 134 including but not limited todocketing server applications, networking information, docketing userdemographic or statistical information, docketing server administratorpermissions, etc.

FIG. 2B further illustrates the potential contents of the intellectualasset records 200. Generally, the intellectual asset records 200 includea set of related data organized into meaningful units which pertain toan intellectual asset such as a patent, a trademark, copyright, or thelike. For example, the set of related data of the intellectual assetrecords 200 may be organized into the meaningful units including arecord identifier 210, an asset type 220, an asset title 230, an assetdescription 240, an asset status 250, a document 260, a task 270, and aprosecution item 290. Each of these meaningful units will be brieflydiscussed below.

With respect to the embodiment illustrated in FIG. 2B, the recordidentifier 210 is an identifier uniquely identifying the intellectualasset record 200 and can be used to reference the intellectual assetrecord 200. The asset type 220 may be used to distinguish betweenvarious types of intellectual assets, such as patents, trademarks,copyrights, trade secrets, etc. The asset title 230 may provide ahuman-readable name for the intellectual asset record 200, and the assetdescription 240 may provide a human-readable summary of the intellectualasset record 200. The asset status 250 may indicate the current statussuch as pending, abandoned, issued, etc. of the intellectual assetassociated with the intellectual asset record 200.

Examples of the document 260 may include but is not limited to anarchive, a record, a report, a paper, an article, a reference, aresponse, an action, a correspondence, a memorandum, an audio recording,a video recording, a photo, or a drawing. The document 260 is associatedwith the intellectual asset record 200 by being linked to theintellectual asset record 200. The link between the intellectual assetrecord 200 and the document 260 can be implemented through varioustechniques which may include, storing in the intellectual asset record200 a file path to the document 260, storing in the intellectual assetrecord 200 a database reference to the document 260, and the like.Additionally, the document 260 may be stored within the intellectualasset record 200 as illustrated in FIG. 2B or alternatively, thedocument 260 may be stored separately from the intellectual asset record200.

In the embodiment illustrated in FIG. 2B there is one document 260associated with the intellectual asset record 200. However, the document260 may be a plurality of documents 260 which may include variousexamples listed above. Additionally or alternatively, the plurality ofdocuments 260 may be associated with one intellectual asset record 200,the plurality of documents 260 may be associated with multipleintellectual asset records 200, or some subset of the plurality ofdocuments 260 may be associated with one or more intellectual assetrecords 200 within the docketing system 100 (FIG. 1). Once the file 205is associated with the intellectual asset records 200, the file 205 isalso referred to as the document 260.

Generally, the task 270 denotes an action for a specified docketing userto complete by a specified time. Some examples of the task 270 mayinclude but are not limited to instructing outside counsel, attendingmeetings, etc. Like the document 260, the task 270 may be a plurality oftasks 270. That is, multiple tasks 270 may be, and commonly are,associated with the intellectual asset record 200.

The prosecution item 290 denotes an action related to the prosecution ofan intellectual asset. The prosecution item 290 may include a signalthat may indicate that an additional prosecution items 290 and/or tasks270 is required following completion of the first prosecution item 290.For example, the intellectual asset record 200 may include a firstprosecution item 290 that, as a result of the first prosecution item290, one or more tasks 270 or a second prosecution item 290 must becompleted.

In alternative embodiments, an intellectual asset record 200 may includea set of related data which may be organized into meaningful units thatmay include any subset of those meaningful units listed above or mayinclude various others not listed. For example, an embodiment of anintellectual asset record 200 may include a record identifier 210, adocument 260, a task 270, and a prosecution item 290 and omit the assettype 220, the asset title 230, the asset description 240, and/or theasset status 250.

As stated above with reference to FIG. 1, the docketing system 100enables the user device 110 to access the docketing server 130 to obtainthe docketing service. Some examples of means to access the docketingserver 130 include a docketing client software and/or a web browserloaded on the user device 110. Alternatively, the user device 110 maycommunicate with the docketing server 130 through a remote desktopconnection. In embodiments with the web browser, the docketing server130 provides the docketing service as a web application.

To provide the docketing service, examples of the docketing system 100may allow the docketing user to interface with the docketing server 130.The interface between the docketing user and the docketing server 130may utilize user interface (“UI”) objects. The UI objects provide thedocketing user information related to a specific meaningful unit such asthe task 270 (FIG. 2B), the document 260 (FIG. 2B), or the prosecutionitem 290 (FIG. 2B). Additionally or alternatively the set of UI objectsmay allow the docketing user to modify the information contained in themeaningful units.

Depending on the configuration of the docketing system 100, the UIobjects may be created and provided to the docketing user differently.For example, the UI objects may be created by the docketing server 130and may be provided to the web browser loaded on the user device 110. Inthis embodiment, the web browser renders the UI objects which may bedescribed in HTML, JavaScript, CSS or an equivalent language. Inalternative embodiments, the UI objects may be implemented as adedicated client on the user device 110 or the UI objects may beimplements by the docketing user interfacing directly with the docketingserver 130.

An example docketing service may be the association of a file 205 withan intellectual asset record 200. This docketing service may utilize UIobjects. In one embodiment of the association of a file 205 with anintellectual asset record 200, the UI objects utilized may include an UIobject providing details of tasks associated with an intellectual assetrecord 200, an UI object for a docketing user to add a prosecution itemto an intellectual asset record 200, and an UI object providing detailsof documents associated with an intellectual asset record 200. Inalternative embodiments, the association of a file 205 with anintellectual asset record 200 may include other UI objects. Details ofassociating a file 205 with an intellectual asset record 200 and the UIobjects utilized therein are disclosed below.

Referring next to FIG. 3, an example of a docketing system performingthe docketing service of associating a file 205 with an intellectualasset record 200 (hereinafter “an associating system”) 300 isillustrated. As depicted the associating system 300 includes a file 205,a controller 132, templates 304, a computer network 120, and anintellectual asset record 200. The associating system 300 will bebriefly introduced, and detailed disclosures are included below.

The controller 132 of the associating system 300 takes as an input thefile 205 which has information pertaining to the file such as a filename 600 and metadata 302. The file 205 which has information pertainingto the file such as a file name 600 and metadata 302 may be transmittedvia the computer network 120 as illustrated in FIG. 3. The file name 600and metadata 302 may have predetermined formats.

Alternatively or additionally, the file 205 may be stored in a memorydevice 134 which may be included in a docketing server 130 coupled withthe controller 132. For example, as illustrated in FIG. 3, a memorydevice 134 may be coupled with a controller 132. The controller 132 mayscan the memory device 134 for a file 205 with a file name 600 ormetadata 302 with the predetermined format or a specific set of metadata302. The scanning of the memory device 134 by the controller 132 mayoccur on a regular schedule, may be triggered as a scheduled process ona docketing server, or may be manually triggered by a docketing user.

The file name 600 includes one or more fields and can be written with apredetermined format which is discussed in detail below with respect toFIG. 6. Generally, the file name 600 may include fields such as areference identifier 610, a document date 620, a document code reference630, and additional file name components 635.

Referring again to FIG. 3, the controller 132 reads the file name 600and extracts one or more of the fields. According to the information inthe extracted fields, the controller 132 associates the file 205 withthe intellectual asset record 200. For example, the controller 132 mayextract the reference identifier 610. From the reference identifier 610,the controller 132 may associate the file 205 with the intellectualasset record 200 having the same or a corresponding record identifier210 through linking the file 205 to the intellectual asset record 200.

Additionally or alternatively, the controller 132 may extract thedocument date 620. The controller 132 may store the document date 620 inthe intellectual asset record 200 as the document date value and/or thedocument date 620 may be stored as a base/mailing date (discussedbelow).

Additionally or alternatively, the controller 132 may extract thedocument code reference 630 from the file name 600. From the documentcode reference 630, the controller may store a document type and adocument description (discussed below) associated with the document codereference 630. Additionally as illustrated in FIG. 3, the controller 132may match the document code reference 630 to one or more templates 304.The templates 304 include information from which a meaningful unit ofrelated data pertaining to an intellectual asset may be organized. Forexample, the templates 304 may include a task template 450 and/or aprosecution template 400 from which a meaningful unit such as a task 270or a prosecution item 290 may be organized.

In an example embodiment, the controller 132 may match the document codereference 630 to a task template 450. Using the task template 450 a task270 associated with the task template 450 may be created in theintellectual asset record 200. In this example, the creation of the task270 in the intellectual asset record 200 may utilize a task list UIobject 418. In alternative embodiments the task 270 may be created inthe intellectual asset record 200 without utilizing the task list UIobject 418.

In another example, the controller 132 may match the document codereference 630 to a prosecution template 400. Using the prosecutiontemplate 400, a prosecution item 290 may be created in the intellectualasset record 200. In this example the creation of the prosecution item290 may utilize a prosecution item creation UI object 429. Inalternative embodiments the prosecution item 290 may be created in theintellectual asset record 200 without utilizing the prosecution itemcreation UI object 429.

Additionally or alternatively, the controller 132 may read the metadata302 pertaining to the file 205. Generally, metadata 302 includes dataabout the file 205 such as an author, a check in comment, a citationstatus identifier, a class, a correspondence date, a country identifier,a description, a document management folder identifier, a documentmanagement status, a document management type identifier, a fileextension, a file size, a file upload type identifier, an issue date, akind code, a link record file identifier, a number type identifier, anoriginal file, an owner, a publication date, a recipient, a sourceidentifier, and a sub-class.

When the controller 132 associates the file 205 with the intellectualasset record 200, making the file 205 a document 260, the metadata 302may define the details of the document 260. Some details may be definedfrom the metadata 302 itself, other details may be providedautomatically based on the contexts of the association of the file 205,and still other details may be manually entered by the docketing user.

The details of the document 260 that may be defined by the metadata 302can include, but are not limited to, an author, a check in comment, acitation status identifier, a class, a correspondence date, a countryidentifier, a description, a document management folder identifier, adocument management status, a document management type identifier, afile extension, a file size, a file upload type identifier, an issuedate, a kind code, a link record file identifier, a number typeidentifier, an original file, an owner, a publication date, a recipient,a source identifier, and a sub-class.

The data about the file 205 included in the metadata 302 such as thefile upload type identifier or issue date can also be used as definedconditions. The defined conditions can indicate to the controller 132 acharacteristic such as the type, kind, category, or nature of the file205. The defined conditions act to triggers the controller 132 toperform one or more defined actions. That is, based on the definedconditions within the metadata 302, the controller 132 performs definedactions that can include, but are not limited to, creating one or moretasks 270, creating one or more prosecution items 290, modifyingvalue(s) in the task list UI object 418, modifying value(s) in theprosecution item creation UI object 429, associating the file 205 withone or more intellectual asset record(s) 200, providing a message to thedocketing user such as composing and/or sending email(s), recording anevent in an intellectual asset record, modifying the set of related dataincluded in an intellectual asset record, and/or associating thedocument 260 with a specific task 270 or prosecution item 290.

For example, a file 205 may be a non-disclosure agreement (“NDA”) withmetadata 302 including an author, a date, and a document size pertainingto the NDA. Moreover, contained in the metadata 302 of the NDA may be adefined condition indicating that the file 205 is an NDA. When the NDAis uploaded, the controller 132 reads the metadata 302 of the file 205.The author, the date, and the document size may define the details ofthe document 260 associated with an intellectual asset record 200.Additionally, based upon the defined condition, the controller 132 mayperform defined actions related to the NDA. Example defined actions mayinclude creating a task 270 for a case manager to review the NDA, and/orthe controller 132 may compose and send an email to a case manager. Theemail may include the author and/or the date contained in the metadata302 of the NDA or alternatively the email may include informationmanually entered by a docketing user or automatically generated based onthe contexts of the association of the NDA.

Additionally, the controller 132 may include a set of rules that dictatewhich defined action the controller 132 performs based on a particulardefined condition. In some embodiments, the controller 132 may enablemodification of the set of rules based on a particular definedcondition.

For example, the docketing user may modify the set of rules such thatwhen a file 205 which is an application draft is uploaded, thecontroller 132 is triggered to perform the defined action of creating atask 270 for a case manager to review the file 205. The docketing usermay establish the particular defined condition as “application draft”and further modify a corresponding rule in the set of rules such thatthe controller 132 is triggered to create a task 270 for a case managerto review the file 205. Thus, anytime a file 205 is uploaded withmetadata 302 including “application draft” as the particular definedcondition, the controller 132 will be triggered to create a task 270 fora case manager to review the file 205. Additional description of thevarious components and items of the associating system 300 are disclosedbelow.

Turning next to FIG. 4A, additional details of the task list UI object418 are disclosed. As illustrated in FIG. 4A, the task list UI object418 provides details on the tasks 270 (illustrated as a first task 270A,a second task 270B, and a third task 270C) associated with theintellectual asset record 200. For example, the task list UI object 418may display information, referred to generally as values, related to thetask 270 such as a due date value 412, a target value 414, and a taskname value 416. Ultimately, the task list UI object 418 relatesinformation with an action that is to be accomplished. The action may bespecifically described by the task 270 in a docketing schedule (notshown).

In the example third task 270C provided in FIG. 4A, the due date value412 is Dec. 8, 2011; the target value 414 is John Smith; and the taskname value 416 is “Application—Final Deadline to Foreign File.” In thisexample, the above values mean that John Smith needs to file a foreignapplication by Dec. 8, 2011 for the intellectual asset associated withthe intellectual asset record 200. In the above example, the action iswhat John Smith needs to do, that is, “file a foreign application” whichmay be described by the task 270 in John Smith's docketing schedule.

The task 270 can be created by the docketing user or automatically bythe docketing server 130. In either case, that is if the task 270 iscreated by the docketing user or automatically by the docketing server130, a task template 450 may be used to create a task 270. FIG. 4Billustrates an example task template 450. As illustrated in FIG. 4B, thetask template 450 may include a task name 455, a task description 460, atask primary target 465, action date information 470, escalationinformation 475, and one or more task document upload codes 480.

When the docketing user or the docketing server 130 utilizes the tasktemplate 450 to create the task 270, the values of the task template 450are used for the task 270. The task name 455 and the task description460 provide a name and description, respectively, for the task 270created from the task template 450. The task 270 is directed to the taskprimary target 465, with dates for the task 270 to be displayed and/orcompleted defined in the action date information 470. The task documentupload codes 480 refer to the document code item 500 which associates adocument 260 with the task 270 described in detail with respect to FIG.5.

Therefore, in the task list UI object 418 for the tasks 270, the taskname 455 is then displayed as the task name value 416, the task primarytarget 465 is then displayed as the target value 414, and the actiondate info 470 determines what is displayed for the due date value 412.If defined, the escalation information 475 provides details onescalation paths to be taken in the case that the task primary target465 does not complete the task 270 by the “to be completed” date whichmay be additionally defined in the action date information 470.

Turning next to FIG. 4C in combination with FIG. 4D, additional detailsof the prosecution item creation UI object 429 and the prosecutiontemplate 400 are disclosed. Generally, the prosecution item creation UIobject 429 and the prosecution template 400 are used to add theprosecution item 290 to the intellectual asset record 200.

First, FIG. 4C depicts an example of the prosecution item creation UIobject 429. As illustrated in FIG. 4C, the prosecution item creation UIobject 429 may include a prosecution template selector 421, abase/mailing date value 422, an action due date value 423, a primarytarget selector 424, a comments value 428, an upload document button431, a link document button 426, and an add button 427. Example functionof each of these items is briefly discussed below.

The primary target selector 424 allows the docketing user to choose atarget for the prosecution item 290. A target is usually an entity orentities responsible for completion of the prosecution item 290. In someembodiments the primary target selector 424 may include a drop-down menuwith potential or available targets that may be selected as a target. Inthe embodiment illustrated in FIG. 4C, the prosecution item creation UIobject 429 allows the docketing user to associate one or more documents260 with the prosecution item 290. If a document 260 is not alreadyassociated with the intellectual asset record 200 (an unassociateddocument) the docketing user may associate one or more unassociateddocuments with the prosecution item 290 through use of the uploaddocument button 431. Additionally, if a document 260 is alreadyassociated with the intellectual asset record 200 but not associatedwith the prosecution item 290 (an associated document), the docketinguser may associate one or more associated documents with the prosecutionitem 290 through use of the link document button 426.

The docketing user may additionally enter a date into the base/mailingdate value 422. The base/mailing date value 422 may correspond to aninitiation date such as the mailing date of a patent office action.Likewise, the docketing user may enter a date into the action due datevalue 423. The action due date value 423 may correspond to a completiondate such as six months from the mailing date of an USPTO office action.The comment value 428 allows the docketing user to add supplementaryinformation to the prosecution item creation UI object 429.

In one embodiment, the docketing user may manually input thebase/mailing date value 422 and the action due date value 423, manuallyselect the target using the primary target selector 424, and/or manuallyassociate documents 260 with the prosecution item 290 using the uploaddocument button 431 or the link document button 426. In this embodiment,when the document user is satisfied with the contents of the prosecutionitem 290, the docketing user may select the add button 427 to createprosecution item 290 containing the above information. Additionally oralternatively, the docketing user may create a prosecution item 290using the prosecution template selector 421 as discussed below.

With combined reference with FIGS. 4D and 4C, through interfacing withthe prosecution item creation UI object 429, the docketing user may usethe prosecution template selector 421 to select the prosecution template400. Generally, the prosecution template 400 includes formattedinformation related to a given prosecution-related action according tolegal or potentially corporate/private standards or preferences. Theprosecution template 400 is used as a basis for creating the prosecutionitem 290. FIG. 4D illustrates an example prosecution template 400 whichmay include an action name 405, an action offset 410, a display offset415, a prosecution primary target 420, one or more sub-actions 425, andone or more prosecution document upload codes 430.

When the docketing user selects the prosecution template 400 using theprosecution template selector 421, and the docketing user selects theadd button 427, the prosecution item 290 is thereby created. Theprosecution item 290 then includes the values determined by theprosecution template 400.

For example, the prosecution item 290 may include the action name 405.By selecting the prosecution template 400, the action name 405 describesthe task name value (416, FIG. 4A) for the task 270 to create andassociate with the intellectual asset record 200. The action offset 410may set a default due date value (412, FIG. 4A) for theprosecution-related action. The display offset 415 in this example canbe set to a configurable date offset for when the primary target 420wants to be alerted of the next task 270 on the docketing schedule,which is usually before the date provided in the due date value 412.

In a more specific example embodiment, the prosecution template 400 maybe a USPTO non-final office action rejection. As a result of creatingthe prosecution item 290 using the prosecution template 400 for thenon-final office action rejection, the task name value 416 for the nexttask 270 could be “File response to non-final office action rejection,”and the action offset 410 in this example would be set to three monthsby default, which would then accordingly set the due date value 412 tothe base/mailing date value 422 value plus the action offset 410.

Additionally, the prosecution template 400 may include one or moresub-actions 425. The sub-actions 425 may include additional tasks 270associated with the prosecution item 290. In the same example, the oneor more sub-actions 425 may include the additional task 270 to instructoutside counsel to file an office action response.

Additionally, as illustrated in FIG. 4D, the prosecution template 400may include one or more prosecution document upload codes 430. Similarto the task document upload codes 480, the prosecution document uploadcodes 430 refer to the document code item 500 which associates adocument 260 with the prosecution item 290 described in detail withrespect to FIG. 5.

Turning next to FIG. 4E, additional details of the document details listUI object 433 are disclosed. As illustrated in FIG. 4E an exampledocument details list UI object 433 may provide details of documents 260(illustrated as a first document 260A and a second task 260B) associatedwith the intellectual asset record 200. For the documents 260 detailedin the document details list UI object 433, there may exist a documentdate value 432, an author value 434, a document type value 435, adocument description value 436, and an upload document button 438.

The document date value 432 provides the base date for the document.Examples of the document date value 432 may include the mailing date ofan office action, the date an application was filed, and the like. Theauthor value 434 provides the name or names of the originator(s),linker(s), or modifier(s) of the document 260. Examples of the authorvalue 434 may include a name of a specific person, a general term suchas “docketing” or “secretarial suite”, or may include general termsrelated to governmental or private entities. The document type value 435provides the general type of the document 260. The document type value435 may be relatively specific or a general term understood by thedocketing users as a type of document 260. The document descriptionvalue 436 is a brief description of document 260 which may be relativelyspecific or a general term understood by the docketing users as acharacterization of the document 260. Generally, the documentdescription value 436 further describes the document type value 435. Theupload document button 438 can be used by the docketing user to uploadthe document 260 and associate the document 260 with the intellectualasset record 200.

In the example second document 260B provided in FIG. 4E, the documentdate value 432 is Feb. 8, 2010, the author value 434 is “System”, thedocument type value 435 is “Office Action”, and the document descriptionvalue 436 is “Non-Final Rejection”. This may mean that the seconddocument 260B is a non-final rejection office action with a base date ofFeb. 8, 2010, and that the docketing server 130 (i.e., “System”) linkedthe document 260 with the intellectual asset record 200.

In alternative embodiments the details of the document 260 may includeany information related to the document 260 including but not limitedto: an author, a check in comment, a citation status identifier, aclass, a correspondence date, a country identifier, a description, adocument management folder identifier, a document management status, adocument management type identifier, a file extension, a file size, afile upload type identifier, an issue date, a kind code, a link recordfile identifier, a number type identifier, an original file, an owner, apublication date, a recipient, a source identifier, and a sub-class. Asmentioned above, the details of the document 260 may be defined bymetadata (302, FIG. 3) of the document 260. Specifically, theinformation related to the document 260 may be defined from the metadataitself, provided automatically based on the contexts of the associationof the file 205, and/or manually entered by a docketing user.

Referring next to FIG. 5, an example document code item 500 isillustrated. Generally, the document code item 500 connects the document260 with an associated prosecution item 290 and/or a task 270 of a givenintellectual asset record 200. Specifically, in one embodiment, theprosecution document upload code 430 (FIG. 4D) and the task documentupload code 480 (FIG. 4B) refer to the document code items 500. Thisreference creates a link between the document 260 having the referenceddocument code item 500 with the prosecution item 290 and/or task 270having the prosecution document upload code 430 or task document uploadcode 480, respectively, referring to the document code item 500.

In the above description, the document code item 500, the prosecutiondocument upload code 430, and the task document upload code 480 arediscussed singularly. However, in alternative embodiments, each of thedocument code item 500, the prosecution document upload code 430 and thetask document upload code 480 may be plural in any combination. That is,a task 270 may have one or more task document upload codes 480. Likewisea prosecution item 290 may have one or more prosecution document uploadcodes 430. Multiple prosecution document upload codes 430 and/or taskdocument upload codes 480 may reference more than one document codeitems 500.

As depicted in FIG. 5, the document code item 500 may include a documentcode 510, a document description 520, and a document type 530. In theexample document code item 500, there are one each document code 510,document description 520, and document type 530. However, in alternativeembodiments, the document code item 500 may include one or more documentcodes 510, document descriptions 520, and document types 530 in anycombination.

The document code 510 is a code that references the type, source(s),etc. of a document 260. For example, the document code 510 “NFR” maymean “non-final rejection from the USPTO.” The document description 520can be utilized to populate the document description value 436 (FIG.4E), and the document type 530 can be used to populate the document typevalue 435 (FIG. 4E).

Referring now to FIG. 6, the fields of an example file name 600 of thefile 205 is depicted. As illustrated in FIG. 6, the file name 600 mayinclude fields such as a reference identifier 610, a delimiter 615, adocument date 620, a document code reference 630, one or more additionalfile name components 635, and a file extension 640. In the embodimentdepicted in FIG. 6 the order of the fields from left to right is aslisted above, however, in alternative embodiments, the order ofinclusion of the fields of the file name 600 may be rearranged.

The delimiter 615 delimits the fields of the file name 600. Anycharacter or combination of characters (e.g., a space character) may beused to delimit the various fields of the file name 600. The referenceidentifier 610 can reference the record identifier 210 (FIG. 2A) of theintellectual asset record 200. The document date 620 provides a base ormailing date pertaining to the file 205 and may be stored as thedocument date value (discussed below). The document date 620 may beformatted according to a predetermined date format such asdate-month-year, year-month-date, etc. The document code reference 630references the document code item 500 by the document code 510. The oneor more additional file name components 635 serve as human-readabledescriptive text. Generally, the additional file name components 635 arenot utilized by the controller 132 (FIGS. 8 and 2A), but can be read bythe docketing user to provide supplemental information about the file205. The one or more additional file name components 635 mayadditionally or alternatively contain the delimiter 615, which may beignored by the controller 132.

The file extension 640 is an extension to a file, which varies by filetype. For example, text files often have a file extension of “.txt”, andportable document format files have a file extension of “.pdf”. All filetypes can be supported, regardless of whether or not a file typeincludes human-readable text.

An example file name according to the file name 600 is “8102485812-03-2010 NFR.pdf”, where “81024858” is the reference identifier 610identifying the record identifier 210, and thereby the intellectualasset record 200; “12-03-2010” is the document date 620; and “NFR” isthe document code reference 630 which in turn refers to the documentcode 510 of a document code item 500. As above, this example, “NFR” as adocument code reference 530 may reference document code 510 for anon-final rejection from the USPTO.

Potentially, a task 270 and/or a prosecution item 290 associated withthe intellectual asset record 200 may have a prosecution document uploadcodes 430 and/or task document upload codes 480 that refer to thedocument code item 500 and may thereby be linked to the file 205 whichfollowing an association with the intellectual asset record 200 would bereferred to as a document 260. Additionally or alternatively, thedocument code item 500 may prompt the automatic addition of one or moretasks 270 or prosecution items 290 to the intellectual asset record 200.

Turning next to FIG. 7 in combination with FIG. 3, additional details ofa method for automatically associating a file 205 with an intellectualasset record 200 are disclosed. Referring to FIG. 7, a flow diagramdepicting an example method 700 for automatically associating the file205 with the intellectual asset record 200 and for automatically addingone or more tasks 270 and/or prosecution items 290 to the intellectualasset record 200. The document association process 700 may be performedby an electronic device, such as the docketing server 130.Alternatively, the document association process 700 may be manuallyinitiated by the docketing user, or may be automatically initiatedaccording to a predefined schedule stored on the one or more of memorydevices 134, with the pre-defined schedule read by the controller 132.

At 702 the document association process 700 begins. At step 704 thecontroller 132 of the docketing server 130 selects a file folder. Thefile folder may be a virtual, digital directory in which files 205 andother file folders can be organized and stored on the one or more memorydevices 134. File folder selection is optional, and is used in the casewhere one or more files 205 have been stored in one or more filefolders. The docketing user may, for example, download a set of filesfrom a prosecution history with a patent office, copy and store the setof files 205 in one or more file folders, and then either manuallyinitiate the document association process 700, or allow the controller132 to automatically initiate the document association process 700according to the predefined schedule. The docketing user can directlyaccess the docketing server 130 through the one or more input devices139 (FIG. 2A) to store the files 205 on the one or more memory devices134, or the docketing user can use remote desktop on the user device 110to connect to and communicate with the docketing server 130 to store thefiles 205 on the one or more memory devices 134. Alternatively, thedocketing user can provide the files 205 to the docketing server 130through a web browser interface (for example, through a drag-and-drop UImechanism) on the user device 110 for a web application running on thedocketing server 130, thereby initiating the document associationprocess 700. Similarly, the docketing user can provide the files 205 tothe docketing server 130 through a docketing client on the user device110, thereby initiating the document association process 700.

Configuration information (not shown) can be stored on the one or morememory devices 134, wherein the configuration information is read by thecontroller 132 and can indicate which file folders to select, whichfiles to skip, which type of date formatting to utilize (e.g.,DD-MM-YYYY, MM-DD-YYYY, YYYY-MM-DD, etc.), and the like.

At 706 the controller 132 scans for the file 205, and then selects thefile 205 and reads the information pertaining to the file 205 such asthe file name 600 and the metadata 302. If at 708 the controller 132determines whether that the file name 600 of the file 205 includes thereference identifier 610 and that the reference identifier 610identifies the record identifier 210 of one of the plurality ofintellectual asset records 200, then at 714 the controller 132 links thefile 205 as the document 260 with the associated intellectual assetrecord 200 referred to by the reference identifier 610.

In an example embodiment, the controller 132 may need to copy or movethe file 205 from a first memory device of the one or more memorydevices 134 to a second memory device of the one or more memory devices134 to link the file 205 with the associated intellectual asset record200.

Using the document date 620, the controller 132 at 715 stores thedocument date 620 pertaining to the file 205 in the intellectual assetrecord 200, which then allows the docketing user to subsequently viewthe document details list UI object 433 to see the document date value432 pertaining to the file 205, now referenced as the document 260.

Additionally or alternatively, at 706, the controller 132 may read themetadata 302 pertaining to the file 205. At 730, the metadata 302 maydefine the details of the file 205 which is referred to as the document260 once associated with the intellectual asset record 200. At 736,whether the metadata 302 includes a defined condition is determined. Ifthe metadata 302 includes a defined condition, at 732, the controller132 may perform one or more defined actions such as creating one or moretasks 270 or composing and/or sending an email.

At 716, if the document code reference 630 is included, and the documentcode reference 630 matches one or more of the one or more prosecutiondocument upload codes 430 or the one or more task document upload codes480, then the controller 132 creates one or more tasks 270 and/or one ormore prosecution items 290 accordingly.

If at 722 another file 205 is to be processed, then processing resumesat 706 to select and read the file 205 and continue subsequentprocessing. If there is not another file 205 to be processed, then at728 if another folder is to be processed, then processing resumes at 704to select the folder and continue subsequent processing.

If at 708 the format of the file name 600 is unrecognized, the documentcode reference 630 is unrecognized, or the reference identifier 610 doesnot reference the record identifier 210 of any intellectual asset record200, then at 734, error information is stored in the one or more memorydevices 134, and processing continues at 722.

Once all folders (if applicable) and all files have been selected andprocessed, the document association process 700 ends at 750 and isconsidered completed.

The embodiments described herein may include the use of a specialpurpose or general-purpose computer including various computer hardwareor software modules, as discussed in greater detail below.

Embodiments within the scope of the present invention also includetangible computer-readable media for carrying or havingcomputer-executable instructions or data structures stored thereon. Suchcomputer-readable media can be any available media that can be accessedby a general purpose or special purpose computer. By way of example, andnot limitation, such computer-readable media can comprise RAM, ROM,EEPROM, CD-ROM or other optical disk storage, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tocarry or store desired program code means in the form ofcomputer-executable instructions or data structures and which can beaccessed by a general purpose or special purpose computer.

Computer-executable instructions comprise, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing device to perform a certain function orgroup of functions. Although the subject matter has been described inlanguage specific to structural features and/or methodological acts, itis to be understood that the subject matter defined in the appendedclaims is not necessarily limited to the specific features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as example forms of implementing the claims.

As used herein, the term “module” or “component” can refer to softwareobjects or routines that execute on the computing system. The differentcomponents, modules, engines, and services described herein may beimplemented as objects or processes that execute on the computing system(e.g., as separate threads). While the system, methods, and other meansfor accomplishing functions disclosed herein are preferably implementedin software, implementations in hardware or a combination of softwareand hardware are also possible and contemplated. In this description, a“computing entity” may be any computing system as previously definedherein, or any module or combination of modulates running on a computingsystem.

FIG. 8 and the following discussion are intended to provide a brief,general description of a suitable computing environment in which severalembodiments may be implemented. For example FIG. 8 may illustrate anexample of various components of a docketing server, a user device, acontroller, or a memory device. FIG. 8 can also illustrate a means andsteps for accomplishing various functionality and acts disclosed herein.For example, FIG. 8 as a specially programmed computer can read a filename of at least one file, extract a reference identifier from the filename, link a file with an intellectual asset record, extract a documentcode from a file name, store a document type and a document descriptionassociated with a document code, extract a document date from a filename, create a task from a task template, create a prosecution item froma prosecution template and scan a memory device for the file having afile name of a predetermined format as well as other acts and algorithmsdisclosed herein. Although not required, several embodiments will bedescribed in the general context of computer-executable instructions,such as program modules, being executed by computers in networkenvironments. Generally, program modules include routines, programs,objects, components, data structures, etc. that perform particular tasksor implement particular abstract data types. Computer-executableinstructions, associated data structures, and program modules representexamples of the program code means for executing steps of the methodsdisclosed herein. The particular sequence of such executableinstructions or associated data structures represents examples ofcorresponding acts for implementing the functions described in suchsteps disclosed herein.

Those skilled in the art will appreciate that the embodimentsillustrated herein may be practiced in network computing environmentswith many types of computer system configurations, including personalcomputers, hand-held devices, multi-processor systems,microprocessor-based or programmable consumer electronics, network PCs,minicomputers, mainframe computers, and the like. Several embodimentsmay also be practiced in distributed computing environments where tasksare performed by local and remote processing devices that are linked(either by hardwired links, wireless links, or by a combination ofhardwired or wireless links) through a communications network. In adistributed computing environment, program modules may be located inboth local and remote memory storage devices.

With reference to FIG. 8, an example of a docketing system forimplementing several embodiments is illustrated, which includes ageneral purpose computing device in the form of a conventional computer820, including a processing unit 821, a system memory 822, and a systembus 823 that couples various system components including the systemmemory 822 to the processing unit 821. The system bus 823 may be any ofseveral types of bus structures including a memory bus or memorycontroller, a peripheral bus, and a local bus using any of a variety ofbus architectures. The system memory includes read only memory (ROM) 824and random access memory (RAM) 825. A basic input/output system (BIOS)826, containing the basic routines that help transfer informationbetween elements within the computer 820, such as during start-up, maybe stored in ROM 824. Such components, or similar components, may alsoembody a workstation for a company representative.

The computer 820 may also include a magnetic hard disk drive 827 forreading from and writing to a magnetic hard disk 839, a magnetic diskdrive 828 for reading from or writing to a removable magnetic disk 829,and an optical disk drive 830 for reading from or writing to removableoptical disk 831 such as a CD-ROM, DVD, or other optical media. Themagnetic hard disk drive 827, magnetic disk drive 828, and optical diskdrive 830 are connected to the system bus 823 by a hard disk driveinterface 832, a magnetic disk drive-interface 833, and an optical driveinterface 834, respectively. The drives and their associatedcomputer-readable media provide nonvolatile storage ofcomputer-executable instructions, data structures, program modules andother data for the computer 820. Although the environment describedherein employs a magnetic hard disk 839, a removable magnetic disk 829and a removable optical disk 831, other types of computer readable mediafor storing data can be used, including magnetic cassettes, flash memorycards, digital versatile disks, Bernoulli cartridges, RAMs, ROMs,millipede memory, and the like.

Program code means comprising one or more program modules may be storedon the hard disk 839, magnetic disk 829, optical disk 831, ROM 824 orRAM 825, including an operating system 835, one or more training andwork management programs 836, other program modules 837, and programdata 838, such as company representative proficiencies and status. Auser may enter commands and information into the computer 820 throughkeyboard 840, pointing device 842, or other input devices (not shown),such as a microphone, joy stick, game pad, satellite dish, scanner, orthe like. These and other input devices are often connected to theprocessing unit 821 through a serial port interface 846 coupled tosystem bus 823. Alternatively, the input devices may be connected byother interfaces, such as a parallel port, a game port, or a universalserial bus (USB). A monitor 847 or another display device is alsoconnected to system bus 823 via an interface, such as video adapter 848.In addition to the monitor, personal computers typically include otherperipheral output devices (not shown), such as speakers and printers.

The computer 820 may operate in a networked environment using logicalconnections to one or more remote computers, such as remote computers849 a and 849 b. Remote computers 849 a and 849 b may each be anotherpersonal computer, a server, a router, a network PC, workstations ofcompany representatives, a peer device or other common network node, andtypically include many or all of the elements described above relativeto the computer 820, although only memory storage devices 850 a and 850b and their associated application programs 836 a and 836 b have beenillustrated in FIG. 8. The logical connections depicted in FIG. 8include a LAN 851 and a WAN 852 that are presented here by way ofexample and not limitation. Such networking environments are commonplacein office-wide or enterprise-wide computer networks, intranets and theinternet.

When used in a LAN networking environment, the computer 820 is connectedto the local network 851 through a network interface or adapter 853.When used in a WAN networking environment, the computer 820 may includea modem 854, a wireless link, or other means for establishingcommunications over the wide area network 852, such as the internet. Themodem 854, which may be internal or external, is connected to the systembus 823 via the serial port interface 846. In a networked environment,program modules depicted relative to the computer 820, or portionsthereof, may be stored in the remote memory storage device. It will beappreciated that the network connections shown are exemplary and othermeans of establishing communications over wide area network 852 forreal-time training, routing of work, and adjustment of incentives.

The previously described versions of the present invention have manyadvantages, including simplifying intellectual asset docketing anddocument association, providing for processing documents in bulk,scheduled batch execution, and automatic docketing task and prosecutionitem creation. The present invention does not require that all theadvantageous features and all the advantages need to be incorporatedinto every embodiment of the invention.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

What is claimed is:
 1. A method, comprising: automatically associating,by a controller of a docketing server, a file with an intellectual assetrecord, the associating comprising: reading, from one or more memorydevices, metadata of a file and a file name of the file that includes apredetermined format including a reference identifier; extracting, bythe controller, the reference identifier from the file name;determining, by the controller, whether the reference identifier matchesthe unique record identifier of a particular intellectual asset recordof a plurality of intellectual asset records that are stored on the oneor more memory devices; in response to the reference identifier notmatching the unique record identifier of a particular intellectual assetrecord of the plurality of intellectual asset records, storing, by thecontroller, an error message in the one or more memory devices; inresponse to the reference identifier matching the unique recordidentifier of the particular intellectual asset record, linking, by thecontroller, the file with the particular intellectual asset record,wherein the particular intellectual asset record includes a set ofrelated data organized into meaningful units pertaining to anintellectual asset; determining, by the controller, whether the metadataincludes a defined condition configured to trigger performance of one ormore defined actions; and in response to the metadata including thedefined condition, performing, by the controller, a defined action basedon the defined condition; and once the file is associated with theintellectual asset record, defining, by the controller, one or moredetails of the file according to the read metadata.
 2. The method ofclaim 1, wherein the file name includes a document date, the methodfurther comprising: extracting the document date from the file name, andstoring the document date as the document date value of the file onceassociated with the intellectual asset record.
 3. The method of claim 2,wherein the file name includes a document code reference that refers toa document code item, the method further comprising: extracting thedocument code reference; determining whether the document code itemincludes one or more of a document description and a document type; inresponse to the document code item including the document description,storing the document description as a document description value of thefile once associated with the intellectual asset record; in response tothe document code item including the document type, storing the documenttype as a document type value of the file once associated with theintellectual asset record; determining whether a match exists betweenthe document code item and one or more of a task template and aprosecution template based on a correspondency between the document codeitem and a document upload code included in the task template and/or theprosecution template; in response to the match existing between thedocument code item and document upload code of the task template,creating in the particular intellectual asset record a task according tothe task template, the task denoting an action for a docketing user tocomplete associated with the file; and in response to the match existingbetween the document code item and document upload code of theprosecution template, creating in the particular intellectual assetrecord a prosecution item according to the prosecution template, theprosecution item denoting an action for a docketing user to completeassociated that is associated with the file.
 4. The method of claim 3,wherein the prosecution item includes a signal indicating that followingthe completion of the prosecution item, a second prosecution itemdenoting a second action for a docketing user to compete is required. 5.The method of claim 3, further comprising: in response to the documentcode item including the document type further displaying in a documentdetails list UI object the document date value and the document typevalue; in response to the document code item including the documentdescription, further displaying in a document details list UI object thedocument date value and the document description value; in response tothe match existing between the document code item and document uploadcode of the task template, further displaying in a task list UI objectthe task, a due date based on the document date value and action dateinformation from the task template, and a task primary target from thetask template; and in response to the match existing between thedocument code item and document upload code of the prosecution template,displaying in a prosecution item creation user interface (UI) object thedocument date value as a base/mailing date, an action due date based onthe document date value and an action offset from the prosecutiontemplate, and a primary target based on a primary target from theprosecution template.
 6. The method of claim 1, wherein the definedaction performed is dictated by a set of rules that is configured to bemodified based on a particular defined condition.
 7. The method of claim1, wherein the intellectual asset is an issued patent or pending patentapplication and the particular intellectual asset record is the set ofrelated data organized into meaningful units which pertain to the issuedpatent or pending patent application.
 8. The method of claim 1, whereinthe intellectual asset is an issued trademark or pending trademarkapplication and the particular intellectual asset record is the set ofrelated data organized into meaningful units which pertain to the issuedtrademark or pending trademark application.
 9. The method of claim 1,wherein the file is included in a set of files stored in a memorydevice, the method further comprising: scanning the set of files storedin the memory device; and identifying the file based on the file namebeing in the predetermined format.
 10. The method of claim 9, whereinscanning the memory device is triggered as a scheduled process on adocketing server, wherein the docketing server includes a controller, amicroprocessor, a memory device and is configured to communicate with adocketing user.
 11. The method of claim 1, wherein the file includes onefile of a plurality of files that are organized and stored in a filefolder, the method further comprising: receiving configurationinformation effective to select for a particular subset of files of theplurality of files; determining whether each of the plurality of filesmeets the configuration information; and in response to a particularfile of the plurality of files not meeting the configurationinformation, skipping the particular file.
 12. The method of claim 11,wherein: the configuration information includes a selection of a subsetof the plurality of folders and a predefined schedule at which filesstored in the subset are scanned.
 13. A docketing server comprising: oneor more memory devices on which files and intellectual asset records arestored; one or more controllers operatively connected to the one or morememory devices and configured to communicate with a docketing user; anda non-transitory computer readable medium having encoded thereoncomputer-executable instructions which, when executed by the one or morecontrollers, cause performance of operations comprising: automaticallyassociating a file with one of the intellectual asset records that isstored on one or more memory devices, the associating including: readingmetadata of a file and a file name having a predetermined formatincluding a reference identifier; extracting the reference identifierfrom the file name; determining whether the reference identifier matchesthe unique record identifier of a particular intellectual asset recordof a plurality of intellectual asset records; in response to thereference identifier not matching the unique record identifier of aparticular intellectual asset record of the plurality of intellectualasset records, storing an error message in a memory device; in responseto the reference identifier matching the unique record identifier of theparticular intellectual asset record, linking the file with theparticular intellectual asset record, wherein the particularintellectual asset record includes a set of related data organized intomeaningful units pertaining to an intellectual asset; determiningwhether the metadata includes a defined condition configured to triggerperformance of one or more defined actions; and in response to themetadata including the defined condition, performing a defined actionbased on the defined condition; and once the file is associated with theintellectual asset record, defining one or more details of the fileaccording to the read metadata.
 14. The docketing server of claim 13,wherein the docketing server includes a first memory device and a secondmemory device, wherein the first memory device is separate from thesecond memory device and one of the first memory device, the secondmemory device, or the controller is located remotely.
 15. The docketingserver of claim 14, wherein the file is stored on the first memorydevice and the particular intellectual asset record is stored on thesecond memory device.
 16. The docketing server of claim 13, wherein: thefile name includes a document date; and the operations further comprise:extracting the document date from the file name, and storing thedocument date as the document date value of the file once associatedwith the intellectual asset record.
 17. The docketing server of claim16, wherein: the file name includes a document code reference thatrefers to a document code item; and the operations further comprise:extracting the document code reference; determining whether the documentcode item includes one or more of a document description and a documenttype; in response to the document code item including the documentdescription, storing the document description as a document descriptionvalue of the file once associated with the intellectual asset record; inresponse to the document code item including the document type, storingthe document type as a document type value of the file once associatedwith the intellectual asset record; determining whether a match existsbetween the document code item and one or more of a task template and aprosecution template based on a correspondency between the document codeitem and a document upload code included in the task template and/or theprosecution template; in response to the match existing between thedocument code item and document upload code of the task template,creating in the particular intellectual asset record a task according tothe task template, the task denoting an action for a docketing user tocomplete associated with the file; and in response to the match existingbetween the document code item and document upload code of theprosecution template, creating in the particular intellectual assetrecord a prosecution item according to the prosecution template, theprosecution item denoting an action for a docketing user to completeassociated that is associated with the file.
 18. The docketing server ofclaim 17, wherein the prosecution item includes a signal indicating thatfollowing the completion of the prosecution item, a second prosecutionitem denoting a second action for a docketing user to compete isrequired.
 19. The docketing server of claim 17, wherein the operationsfurther comprise: in response to the document code item including thedocument type further displaying in a document details list UI objectthe document date value and the document type value; in response to thedocument code item including the document description, furtherdisplaying in a document details list UI object the document date valueand the document description value; in response to the match existingbetween the document code item and document upload code of the tasktemplate, further displaying in a task list UI object the task, a duedate based on the document date value and action date information fromthe task template, and a task primary target from the task template; andin response to the match existing between the document code item anddocument upload code of the prosecution template, displaying in aprosecution item creation user interface (UI) object the document datevalue as a base/mailing date, an action due date based on the documentdate value and an action offset from the prosecution template, and aprimary target based on a primary target from the prosecution template.20. The docketing server of claim 13, wherein the defined actionperformed is dictated by a set of rules that is configured to bemodified based on a particular defined condition.
 21. The docketingserver of claim 13, wherein: the intellectual asset is an issued patentor pending patent application and the particular intellectual assetrecord is the set of related data organized into meaningful units whichpertain to the issued patent or pending patent application; or theintellectual asset is an issued trademark or pending trademarkapplication and the particular intellectual asset record is the set ofrelated data organized into meaningful units which pertain to the issuedtrademark or pending trademark application.
 22. The docketing server ofclaim 13, wherein: the file is included in a set of files stored in amemory device; and the operations further comprise: scanning the set offiles stored in the memory device; and identifying the file based on thefile name being in the predetermined format, wherein scanning the memorydevice is triggered as a scheduled process on a docketing server,wherein the docketing server includes a controller, a microprocessor, amemory device and is configured to communicate with a docketing user.